Extensible configuration engine system and method

ABSTRACT

Methods and systems are provided for facilitating decision making through an improved recommendation system. The data used in the system, such as the questions and business logic for navigating between questions, is stored in relational database tables that are easy to access and edit by users. A backend application program reads the data and processes the navigation logic depending upon answers received from users to automatically generate a decision tree. Users are allowed to select questions earlier in the tree, and the application can regenerate a tree from the point of the selected question and on. The application program stores the questions to be presented in a structured document which is handed off to a user interface generation program.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This is a continuation of U.S. patent application Ser. No. 11/313,268,filed on Dec. 19, 2005, which application is incorporated herein byreference in its entirety. This application is related to the followingpending applications, each of which is hereby incorporated herein byreference in its entirety:

Application Ser. No. 09/354,058, titled Hierarchical Backup AndRetrieval System, filed Jul. 15, 1999, attorney docket number 4982/5;

Application Ser. No. 10/818,749, titled System And Method ForDynamically Performing Storage Operations In A Computer Network, filedApr. 5, 2004, attorney docket number 4982/35;

Application Ser. No. 60/519,540, titled System And Method For PerformingIntegrated Storage Operations, filed Nov. 13, 2003, attorney docketnumber 4982/40P;

Application Ser. No. 60/567,178, titled Hierarchical System And MethodFor Performing Storage Operations In A Computer Network, filed Apr. 30,2004, attorney docket number 4982/54P;

Application Ser. No. to be assigned, titled System And Method ForPerforming Multistream Storage Operations, filed Nov. 7, 2005, attorneydocket number 4982-59;

Application Ser. No. to be assigned, titled Method And System Of PoolingStorage Devices, filed Nov. 7, 2005, attorney docket number 4982-61;

Application Ser. No. to be assigned, titled Method And System ForSelectively Deleting Stored Data, filed Nov. 7, 2005, attorney docketnumber 4982-67;

Application Ser. No. to be assigned, titled Systems And Methods ForRecovering Electronic Information From A Storage Medium, filed Nov. 7,2005, attorney docket number 4982-68;

Application Ser. No. to be assigned, titled Method And System ForMonitoring A Storage Network, filed Nov. 7, 2005, attorney docket number4982-66; and

Application Ser. No. to be assigned, titled Systems And Methods ForGenerating Configuration Metrics In A Storage Network, filed Dec. 19,2005, attorney docket number 4982-87.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains materialwhich is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosures, as it appears in the Patent and TrademarkOffice patent files or records, but otherwise reserves all copyrightrights whatsoever.

BACKGROUND

The invention disclosed herein relates generally to automatedrecommendation systems and, more particularly, to improved methods forgenerating decision trees and for allowing more flexible navigation ofsame by users.

Users or purchasers of complex software systems are often called upon tomake difficult decisions. These include such issues as what and how manysoftware components they need or otherwise should license, how and whereto install those components, and how to configure the installedcomponents for optimal benefit. Two typical sources of assistance inmaking these decisions are customer service representatives of thesoftware vendor and documentation provided by the vendor. Customerservice representatives have to be thoroughly trained to provide properassistance and need to be available to assist when the user desires it.Documentation is often very lengthy and is necessarily non-customizedfor each particular user's needs. Either way, both methods are timeconsuming and prone to some errors or, at the very least, result innon-optimal decisions.

Wizards, templates, expert systems, and similar software tools aresometimes employed to assist users in installing or configuring asoftware system. These tools are developed in advance by programmers andwalk users through a process by asking for certain information andreaching conclusions or taking action based on the answers users provideto these questions. The conclusions reached or actions taken arepreprogrammed into the software tool, as are the sequence in which thequestions are presented to users.

Such wizards are useful in walking users through a simple process.However, for more complex processes which have many permutations thatare dependent upon answers provided by users, such wizards or tools aretoo difficult to preprogram or are otherwise inadequate. In addition,such wizards are not designed to allow users to change the conclusionsbased on changes to some answers already provided without redoing theentire decision making process and re-presenting all the questions fromthe beginning. Thus, for example, a wizard designed to assist a user ininstalling a complex software system on a network would ask a series ofquestions related to the configuration of the network upon which thesoftware is to be installed. However, should the configuration change, auser would typically be required to rerun the entire wizard and provideall the network configuration data all over again.

In addition, such wizards or expert systems are preprogrammed by thevendors who supply the software to be installed or configured. As aresult, they do not easily allow a mechanism for an administrator withinan organization to customize the tool for his or her own organization.

As a result, there is a need for improved software tools that simplify adecision making process, facilitate better decision making in the eventof changed circumstances, and allow greater flexibility to systemadministrators.

SUMMARY

The present invention includes methods and systems for facilitatingdecision making through an improved recommendation system. The data usedin the system, such as the questions and business logic for navigatingbetween questions, may be stored in relational database tables that areeasy to access and edit by users. A backend application program readsthe data and processes the navigation logic depending upon answersreceived from users to automatically generate a decision tree. Users areallowed to select questions earlier in the tree, and the application canregenerate a tree from the point of the selected question and on. Theapplication program stores the questions to be presented in a structureddocument which is handed off to a user interface generation program.

In one embodiment of the invention, a computerized method is providedfor facilitating decision making by presenting questions to andreceiving answers from a user. The method involves storing one or moreuser-editable question tables containing a plurality of questions andnavigation logic data for navigating between questions; and maintainingone or more dynamic tables containing question history data identifyingwhich of the questions have been presented in a decision making sessionand answer data identifying answers received from the user. At a givenpoint in a decision making session, one or more questions are selectedto present based on the question history data and the navigation logicdata, and a structured document like an XML file is generated containingthe one or more questions determined to be presented. The structuredocument is used to generate a user interface for presenting the one ormore questions and receiving the answers.

The user-editable question tables may include one or more tables, suchas a table containing the plurality of questions, another tableincluding question options, and yet another table containing thenavigation logic data. A first question table may contain question typedata. A second question table may include expected answers or questionoptions for each question in the first table. The first and secondtables (which may also be one table or more than two tables) may alsostore profile link data identifying groups of entities to whichquestions relate and the dynamic tables maintain separate questionhistory data for different groups of entities based on the profile linkdata. For example, profile links may be created for particular standardsystem types, or component types, etc., such as MICROSOFT FILE SYSTEM,MICROSOFT EXCHANGE servers, SQL servers, or other system types orcomponent types. In some embodiments, the user-editable question tablesstore, in the navigation logic data, jump question data identifying oneor more jump questions to be presented after a given question and callquestion data identifying one or more questions to be presented beforethe given question.

Another table, such as an expression table, may be stored containingexpression data including a plurality of expression data components andone or more expression operators linking the expression data components,the expression data evaluating an expression as true or false based onany of the answers, or may evaluate integers, string values, or otherresponse values. The dynamic tables may then store a link to anexpression data entry in the expression table, and the step ofdetermining which one or more questions to present includes determiningwhether the expression corresponding to the linked expression data entryevaluated to true or false or some other value.

In accordance with aspects of the invention, users are allowed to selecta question previously presented during the decision making session to bepresented again at any point during the decision making session. Thenavigation logic data may be used to determine which one or morequestions to present before or after the user's selected, previouslypresented question. This may be done by comparing an answer received inresponse to the previously presented question to a second answerreceived for the same question presented based on the user selection anddetermining which question to present based on whether the first answeris the same as the second answer.

In accordance with another aspect of the invention, a computerizedmethod is provided for facilitating decision making. The method involvespresenting, in a user interface, a decision tree representing a seriesof information requests presented to a user as part of a decision makingsession, and presenting the information requests to the user in asequence provided by the decision tree. Information is received from theuser in response to at least some of the presented information requests.The user is allowed to select a first information request in thedecision tree that has already been presented in the decision makingsession. The user provides the first information in response to theselected first information request. It is then determined whether thefirst information received from the user results in a change to thedecision tree, and the decision tree is modified based on the firstinformation.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention is illustrated in the figures of the accompanying drawingswhich are meant to be exemplary and not limiting, in which likereferences are intended to refer to like or corresponding parts, and inwhich:

FIG. 1 is a block diagram representing a decision making system inaccordance with one embodiment of the present invention;

FIG. 2 is a representation of database tables employed in the system ofFIG. 1 in accordance with one embodiment of the present invention;

FIG. 3 is a flow chart showing a process for generating and navigating adecision tree in accordance with one embodiment of the presentinvention;

FIG. 4 is a flow chart illustrating a process for navigating in adecision tree when a user selects a question that has already beenanswered, in accordance with one embodiment of the present invention;

FIG. 5 is a flow chart illustrating a process for generating a reviseddecision tree in response to a user selecting a question previouslytraversed, in accordance with one embodiment of the present invention;

FIG. 6 is a flow chart illustrating a process for evaluating expressionsbased on answers received, in accordance with one embodiment of thepresent invention; and

FIG. 7 is a flow chart illustrating a process for making recommendationbased on answers received, in accordance with one embodiment of thepresent invention.

DETAILED DESCRIPTION

In the following description of preferred embodiments, reference is madeto the accompanying drawings that form a part hereof, and in which areshown by way of illustration embodiments in which the invention may bepracticed. It is to be understood that other embodiments may be utilizedand procedural and structural changes may be made without departing fromthe scope of the present invention.

The present invention provides recommendation methods and systems forimproved automated decision making. The use of this invention is notlimited to any particular subject of the decision making, although theinvention is well suited to making decisions with respect to purchase,installation or configuration of a software system in a complex, dynamicenvironment such as a large network. An example of such a system is astorage system used, for example, to perform storage operations such asbackups, archives and restores of data on a network. Such storagesystems are offered by the assignee of the present invention, CommvaultSystems of Oceanport, N.J., and are further described in the commonlyowned patent applications referenced above.

Referring to FIG. 1, a recommendation system 10 in accordance withembodiments of the invention includes a number of discrete software anddata components which interoperate to present information requests tousers, receive responses to those requests, and make recommendationsbased on the responses. The software components in the recommendationsystem 10 are split between a backend application 15 and a front endapplication 20. At a high level, the backend application 15 isprogrammed to process the decision making data and the front endapplication 20 is programmed to generate a user interface and tointeract with a user. The data for the recommendation system 10 isstored in a set of static database tables 25 and a set of dynamicdatabase tables 30. The data may be stored, for example, in a computerreadable medium or other data components known in the art. As describedin greater detail below, the static tables 25 contain questions to bepresented, business logic used in navigating between questions,expression data used in evaluating responses, recommendation data usedin making decisions based on the evaluated expressions, and profile dataused to profile certain types of elements for common questioning orrecommendations. As used herein, questions include any type of requestfor information, regardless of whether the request is phrased in theform of a question. The dynamic tables 30 contain dynamic data usedduring a decision making session, to keep track of questions alreadypresented, questions to be presented, and answers received. As usedherein, a decision making session generally connotes a logicalrelationship among a set of questions being presented, and is notintended to connote or require any temporal relationship between thequestions or any other technical requirement for connecting thequestions.

In operation, the backend application 15 reads the data from the staticdatabase tables 25 and establishes decision tree data which it stores inone or more files 32 which may be communicated using a socket protocol,or alternatively, the data may be stored in XML files 35, or otherfiles. Among other things, as explained further below, the files 32 andXML files 35 contain data on questions to be presented and thenavigational relationship between the questions. The backend application15 provides the files 32 or XML files 35 to the front end application20. The front end application 20 includes instruction code for readingthe data in the files 32 or XML files 35 and automatically generating agraphical user interface (GUI) 40 to present the questions provided inthe files 32 or XML files 35 and to receive answers to the questions.The files 32 or XML files 35 contain some questions to be presented fora given session, and the answers to the questions received through theGUI 40 are handed off to the backend application 15. The backendapplication 15 stores the answers in the dynamic tables 30 anddetermines what questions to navigate to next based on the answers andthe navigational data stored in the static tables 25. The backendapplication 15 also processes the answers to obtain recommendations fordecisions, as explained further below.

In some embodiments, the generated GUI 40 also displays a decision treegraphical image, as represented in FIG. 1, that shows the user thesequence of questions that have been presented so far at any given pointin the process. The decision tree image is built by the front endapplication 20 by reading the data in the files 32 or XML files 35. TheGUI 40 allows the user to choose to answer the next presented question,or to select a previously presented question in the decision tree and toprovide an updated answer where an answer had already been provided orto provide an answer when no answer had been provided.

The use of the XML file format allows for the GUI 40 to be generatedusing a variety of application types. For example, conventional Javatools such as Java Server Faces technology available from SunMicrosystems may be used to parse the XML files 35, retrieve thequestions and other data components, and generate an appropriate userinterface to present those components using styles selected by anadministrator. One skilled in the art will recognize that other fileformats may and other GUI generation technology may be used for the samepurpose and are within the intended scope of the present invention.

A more detailed breakdown of the type of tables that are in the staticdatabase tables 25 and dynamic database tables 30 is shown in FIG. 2.These tables may form part of any conventional relational database, suchas a SQL database, e.g., SQLLite or MySQL. The static tables 25 includeone or more question tables 50 for storing questions and data associatedtherewith such as answers or options associated with questions, one ormore question navigation tables 55 for storing navigation logic used ingenerating the decision tree, one or more profile tables 60 used inallowing users to link together types of elements based on a commonprofile, one or more expression tables 65 for storing logic used inevaluating the answers to facilitate further question navigation andrecommendations, and one or more recommendation tables 70 for storingrecommendation data. The static tables 25 are populated by data providedby a software vendor or by an administrator, and are not changed by thedecision tree generation process.

The dynamic tables 30 include one or more question history tables 75 fortracking what questions have been presented at any given point in adecision making session, one or more answer tables 80 for storinganswers received from users, one or more question stack tables 85 formanaging the question navigation decisions, and one or more profiletables 87, as explained further below. The dynamic tables 30 arepopulated by the backend application 15 during a decision makingsession, and are used by the backend application to select questions topresent at any given point and to make recommendations.

Specific embodiments of tables used in the present invention are nowdescribed. In some embodiments, the question tables 50 include aquestions table and question options or question answer table.Questions, including question text, may be stored in the questionstable. The question table contains a question identifier, question text,a question link text which is a one or two word summary of the questionto display in a question history list as described below, the questiontype or other question related fields. Table fields described herein areexemplary and persons of skill in the art may recognize that fewer oradditional fields may be used to provide the systems and methodsdescribed herein. The question type represents the type of question andwhat type of answer is appropriate for it. For example, the questiontype may include a list of options (perhaps presented as radio buttonsto the GUI), yes/no, numeric or string entries, and a concept of profilelinks which will be explained later. Each question in the questionstable generally has at least one question option or answer. In mostcases, there are multiple answers to choose from. The question option(or answer) table stores a question option identifier (which may serveas the primary key for the table), an associated question identifier, anexpression identifier (e.g., whether the option is active or not,whether an expression whether an option should be displayed or not), aprofile link question identifier, or other field relating to a questionoption. The question identifier may be used to link entries or recordsin the question option table with a one or more records in the questiontable. For example a first question is linked to an entry for questionoptions to the first question. The expression identifier may be used tolink a record or entry in the question option table with one or morerecords in the expression tables 65 and the profile link identifier maybe used to link a record in the question options table with one or morerecords in a profile table 60, or profile 87, both as explained furtherbelow.

In some embodiments, the question navigation tables 55 includes aquestion navigation table containing the following fields: navigationidentifier (which may serve as a primary key for the table), questionidentifier from which to navigate, expression identifier, a jumpquestion identifier, call question identifier, or other field. Thequestion identifier from which to navigate field generally identifies aquestion the navigation table record represents logic for navigatingfrom. Generally, the question identifier of the then most recentlypresented question is used to locate the navigation table record whichcontains the logic for selecting a next question or questions to presentin a GUI. The expression identifier field links a navigation record to arecord in the expression table which is used to evaluate an expressionbased on answers provided to questions presented. If the linkedexpression is true or otherwise provides a value which indicates that asubsequent question be presented, the backend application 15 selects thejump or call question or questions, as explained further below,identified in the questions table as matching the jump questionidentifier or call question identifier, respectively. If the expressionlinked by expression identifier evaluates to false or otherwise providesa value which indicates that a subsequent question be presented, thebackend application 15 selects the jump or call question or questionsidentified in the questions table as matching the jump questionidentifier or call question identifier appropriate for such scenario.

Generally, jump questions are selected to be next presented to a user,e.g., in a GUI, following which navigation goes, or jumps, to adifferent navigation record corresponding to the jump question, whilecall questions are called to be presented without leaving the currentnavigation record. For example, at a given point in the navigation of adecision tree, one or more call questions are presented first to obtaininformation which may then be evaluated to determine which jump questionor questions to pursue next. The process for using these questions isexplained in greater detail below.

In some embodiments, the profile tables 60 include a profile table, aprofile links table, and a profile link list table which is generated atruntime. A user may have one object for which he might answer a set ofquestions one way and another object where he might want to answer someof these questions in a different way. In both cases, the createddecision tree may be quite different. Answers for two objects of thesame kind should be profiles of the same profile type. The profiletables 60 are used to associate user or system profiles of a certainprofile type to a question. For example, a question could be “Pleaseselect all objects of object type A where condition C applies” where theuser is presented with a list of all profiles created of profile type Aand he can choose which profiles of type A apply to the condition. Inanother example, a user may be presented with a question such as “Pleaseselect all server components of brand X in use in your system” or“Please indicate the software modules in use for a particular device inyour system,” or other question. The information input in response tosuch profile questions may be stored in a dynamic user profile table,e.g., 87. Such profile information is accessed by the frontend andbackend to supply user appropriate questions, question options andrecommendations. The profiles selected or input by a user can be usefulin determining recommendations, as described further below.

Profile type is a static entity which may have a name and an identifier,e.g., SQL servers, EXCHANGE servers, data agents, or other identifiers.The static profile table typically includes the following fields:profile identifier (which may be a primary key for the table), profiletype identifier, profile name, profile quantity, question historyidentifier, or other field. The question history identifier may be useda user exits the questioning and opens it again for a particular profileso that the questioning starts where the user left off. The profilelinks table may be used to link profile records stored in the profiletable with question records in the questions table and may have fieldsincluding: a profile link identifier (which may be the primary key forthe table), a profile type identifier to link the table to one or moreprofile records and to list profiles from, and a flags column. Theprofile link list table contains a row identifier (which may be aprimary key for the table), a profile link identifier, a profileidentifier, a linked profile identifier and a number of instances thatallow the user to say how many objects or elements have the object typeselected, or other fields.

The expression tables 65 include, in some embodiments, an expressiontable and an expression component table. Generally, expressions useinformation stored in the dynamic answers (or question options) table 80and manipulate those answers or options to determine whether certainquestion options are displayed or not, how to navigate among questions,what recommendations to issue, etc. Whenever an expression may beevaluated in the above cases, an expression identifier is included inthe record or table entry to be linked to a record or records in theexpression table. Thus, for example, the question navigation table hasan expression identifier to link it to one or more expressions itevaluates in deciding which call or jump questions to navigate to. Auser profile 87 may be used to further link expressions to beappropriate for a user's particular system configuration. For example,profile data which indicates that a user operates SQL servers, may linkto expression table entries relating to SQL servers, and not, forexample, ORACLE servers or other servers.

The expression table has an expression identifier field, (which may bethe primary key for the table), an expression description field intendedto include a descriptive text as to what the expression evaluates (to beused in a question editor), a root expression identifier field, or otherfield. The root expression identifier may be the expression identifierof the top level expression needed in the case that an expressionconsists of multiple expressions connected by a Boolean OR operation, orother logical connector.

The actual expression logic is contained in the expression componenttable. One expression identifier can have multiple expressioncomponents, and all expression components for a given expressionidentifier may be connected via a Boolean AND operation or other logicalconnector. The expression component table has the following fields:expression component identifier (which may serve as the primary key forthe table), expression identifier, which links the records to one ormore records in the expression table, an operator, and the followingexemplary expression components:

Comp1_QuestionOptionidentifier Comp1_ExpressionidentifierComp1_Questionidentifier Comp2_QuestionOptionidentifierComp2_Expressionidentifier Comp2_Value_int Comp2_Value_strOR_Expressionidentifier

Referring to the above expression components, component 1 data retrievesthe provided answers and compares it against the values stored in thecomponent 2 using the operator data. The operator field may be, in someembodiments, a 32 bit integer which may be part value and part bitmask,and may operate like the instruction code of a microprocessor. Two bitsdetermine which comp1 input to use (e.g., whether to use a questionoption identifier, an expression identifier or a question identifier)and another two bits which comp2 input to use. One bit in the Operatoris used to negate the comp1 input (to allow for a Boolean NOT), and onebit to similarly negate the comp2 input. Eight bits of the Operator maybe used to represent the actual operation (less than, higher than,equals, AND, OR etc.) used for each expression component. The remainingbits may be available for other use.

In order to connect or associate multiple components together using an“AND” logical association, multiple expression components are provided.To use an “OR” one or more expression components together, the secondexpression component is assigned its own expression identifier and theOR expression identifier entry is used to identify another expressionidentifier to connect such items. When determining if a particularquestion answer affects any expressions, expressions may be joined usingcomp1_QuestionOptionidentifier and comp2_QuestionOptionidentifier, orother field identifying question options. If a sub expression in an ORoperation is used, a root expression identifier may be used to determinean expression identifier that may have changed.

Based on the stored question answers, a user profile, and theexpressions, recommendations are provided. The recommendation tables 70include a recommendations table and a recommendation categories table.The recommendation table may include the following fields:recommendation identifier (which may serve as the primary key for thetable); recommendation category identifier, which links to a record orrecords in the recommendations category table; recommendation text;expression identifier; recommendation importance, or other field. Theexpression identifier may link to one or more expressions in theexpression tables 65. When the expression with the expression identifierbecomes true or other value is presented (e.g., an integer, stringvalue, or other value), then a recommendation is triggered. Therecommendation importance field is used, in some embodiments, to attachlevels of importance attached to a recommendation. These could be, forexample, critical, major, normal, and low, or other level, and are usedfor display purposes.

In some embodiments, recommendations can be grouped into categories. Therecommendation categories table contains the fields such as arecommendation category identifier (which may serve as the primary tablekey and may link to records in the recommendations table), categorytitle, category description, category scope bitmask, or other field. Thedata in the category title and category description fields may be usedto create a user readable report. If one or more recommendations becometriggered to an active state because its associated or linked expressionbecomes true or other appropriate value, a header and description of thecategory could be placed in front of the recommendations, for examplefor a report that is printed at a printer, emailed in an html document,or otherwise provided to a user.

The category scope bitmask may be used to limit a recommendation, forexample, to avoid overwhelming user with multiple recommendations. Forexample, if a user has three profiles in one profile type A and twoprofiles in another profile type B, and would like a list of genericrecommendations all profile types, then very specific recommendationsfor a particular profile might not be of interest to such a user. If,however, a recommendation for one or more profiles triggers arecommendation which would recommend that some global option isrequired, then all recommendations may be displayed. There are generallyseveral bits for the scope of a recommendation, including:

Always show this recommendation

Show this recommendation when getting recommendations for a profile type

Show this recommendation when getting a recommendations on a profilelevel.

The data in the static tables 25 may be edited by a user such as anadministrator, and may be restricted to certain authorized users, e.g.,a person having access to the backend. This allows users to modify anyaspect of the decision making tree without having to rewrite source codeor otherwise engage in programming. For example, new questions may beadded by simply adding appropriate entries in the questions table.Navigation among questions may be easily changed by editing the relevantnavigation entries in the question navigations table. The nature of therecommendations to be given may be changed through edits to therecommendations tables 70, and how answers are used may be changed byediting the expressions tables 65. This provides a flexible, easy to usearchitecture for controlling and customizing a decision making process.

As discussed above, the dynamic tables 30 are used by the backendapplication 15 to store data needed during a decision making session. Insome embodiments, there are cour dynamic tables. The question historytable 75 contains fields, such as question history identifier (which mayserve as the primary key for the table), profile identifier, sectionidentifier, stack identifier, question identifier, or other field. Thebackend application 15 keeps track of the current question through thequestion identifier and the profile linked to that question through theprofile identifier, or other table entry. The stack identifier may linkthe question stack table 85, as explained further below.

The answer table 80 has, the following fields: answer identifier (whichmay serve as the primary key), question option identifier, profileidentifier, value integer, value string, option state, or other field.The question stack table 85 may be used to store called questions. Itsfields include stack identifier, profile identifier, parent stackidentifier, navigation identifier, part, history, history identifier, orother field. The use of these fields is explained in detail below withreference to the processes for navigating among questions and makingrecommendations as illustrated in FIGS. 3-7.

Referring, then, to FIG. 3, a process in accordance with the presentinvention of generating and presenting questions starts by retrievingquestion and navigation data, step 100. As discussed above, the questionand navigation data may be stored in static relational database tables,or other database table, and, in some embodiments, the questionsretrieved are selected in accordance with a specific profile of elementsor objects which are the subject of the decision, or in accordance witha user's profile. The questions retrieved may include all questions in agiven decision tree or a first set of questions which, as determinedfrom the navigation data, are not dependent upon the answers provided.The retrieved questions are stored in a file or an XML file, step 105,along with the appropriate tags to label the questions. The navigationdata may also be stored in the XML file, in some embodiments.

The XML file is then handed off to another application which generates aGUI to present the questions and, if available, the navigation data,step 110. Alternatively, a file may be transmitted using one or moresockets to a front end to generate a GUI. The application generates theGUI and presents the questions, step 115. Users provide answers to thequestions through the GUI, step 120. The answers are stored and thequestion presented is recorded as part of the question history, step125. The next question to present, if any, is determined, step 130,either from the XML file or by the backend application consulting thequestion navigation data. As explained above, in some embodiments thequestion navigation data references an expression to be evaluated basedon received answers and decides which question to select based onwhether the expression evaluates to a value of true or false, an integervalue, string value or other value. If the question navigation datacontains one or more call questions, those call questions may be pushedto the question stack table and become the next questions to be asked.In addition, the current history identifier of the calling question, theparent stack identifier and the profile identifier may be stored in thequestion stack table. After the call question or questions pushed on thestack are presented and answered, navigation returns to the same point,e.g., the same record in the question navigation table, and furtherquestions, e.g., jump questions, may be selected to be presented next,depending upon the value of the expression linked by the expressionidentifier.

The outcome of this navigation process is to proceed to the nextquestion in the decision tree, step 135. The process of presentingquestions, receiving answers and making navigation decision iteratesuntil all questions in the tree are exhausted, e.g., the navigation datafor a given question indicates it is the last question to be presented.When that happens, the backend application retrieves the recommendationsto be made, step 140, based on the answers provided.

In accordance with advantageous aspects of the present invention, a usermay, at any point during a decision making session, select a question toanswer other than the then-currently presented question. In someembodiments, this is done by showing the user through the GUI thedecision tree that he has traversed during the session, by adding eachquestion to the tree as it is presented. The user may then interactthrough the GUI to select a question previously presented. This would bedone by the user for a number of reasons, such as because the userrealized he provided incorrect or incomplete answers to questions, theanswers to the question have changed due to changes in systemconfiguration or the like, or because answers to certain questions wereunavailable at an earlier time or were otherwise not provided.

FIG. 4 illustrates one embodiment of a process for navigating a decisiontree once a user has requested a question previously answered. The userselects the question, step 150, through any known interaction such asmouse clicking on an object representing the question on a display ortyping in data identifying the question. Next, a check is made todetermine whether there were previous question answers for the samequestion, step 155. This is done, in some embodiments, by querying theanswers table described above. In case there are previous answers, theseare removed and replaced with the current answer(s), step 160, byupdating the appropriate record in the answers table. In addition, therecord in the answers table is modified to indicate which questionoption identifiers changed as a result of the new answer, step 165. Thishelps determine which expressions might be affected by the changedanswer.

Next, the navigation data is checked to determine which question(s) tonavigate to next based on the selected question and answer provided.This is done, in some embodiments, by querying the question navigationtable to locate all records in which the question identifier to which tonavigate matches the question identifier of the selected question, step170. For each such record, checked in order of a navigation identifier,step 175, the expression identifier is retrieved and the correspondingexpression in the expression table evaluated to either true or false orother value, step 180, based on the updated question option identifiersin the answers table.

If the question navigation table record has any call questionsidentified, step 185, the call question identified by the call questionidentifier or the alternative call question identified by the callquestion identifier is selected based on whether the expression is trueor false or other value, respectively, step 190. Whichever call questionis selected, the navigation identifier and data identifying whether thecall question is the else call question or not, is stored in thequestion stack table, step 195. The call question or questionsidentified are then presented in sequence to the user, step 200. Oncethe call questions are finished being presented and answers arereceived, navigation returns to the record in the question navigationtable having the navigation identifier pushed to the stack, step 205.Then, the expression identified by the navigation table record isreevaluated, step 210, to determine whether the answers received fromthe call question changed the expression. Depending upon the value ofthe expression, navigation control then jumps to the question given ineither the jump question identifier (when the expression is true or someother preset value), or jump to the question identified by the else jumpquestion identifier, step 215 (e.g., when the expression is false orother preset value). If an expression is false but no jump or callquestions exist, then the next row in the question navigation table ischecked.

Question navigation may get more complicated if a user answered somequestions and then went back to do questions over which would cause adifferent question navigation/decision making tree. FIG. 5 illustratesan alternative process for navigating which includes building a reviseddecision tree based on a user selecting to answer a question alreadyanswered or for which no answer was previously provided. First, the userselects the previously presented question in the decision tree, step250, in the fashion described above. When the question is answered, itis first determined if answers have changed, step 255. If yes, then theold question answers are invalidated, step 260, by, in some embodiments,deleting those records from the answers table. A list of expressionswhich could possibly be affected by this question answer change isgenerated, step 265, by, in some embodiments, querying the expressionstable for the relevant question identifiers.

All question navigation rows which use a potentially affected expressionand which also affect any question navigation within the currentquestion stack are then retrieved, step 270, and the expressions arereevaluated in order of a question history identifier, step 275. If theevaluation of expressions does not result in a change in navigation,step 280, the question history identifier may remain the same and theanswers are updated, accordingly, step 285. If, however, any questionnavigation changes, then the question history in the current stack isinvalidated from that point onwards, step 290.

In the case of a call question being changed, step 295, the entire listof called questions from a question is generated, step 300, and comparedagainst the previous list of called questions, step 305, which, in someembodiments, is stored in the question stack. If a previous callquestion is no longer made, then the answers given to that call questionare recursively invalidated, step 310. In some embodiments, thatincludes invalidating answers to call questions no longer made as wellas any answers provided to questions presented based on the answersgiven to call questions no longer made. The process for determiningwhich answers are affected is the same as one used in generating thedecision tree, as described above. If a new call question is made fromthe current question, step 315, then the first new call question is thenext question presented to the user, step 320, by adding that callquestion to the question stack. If a call question becomes active thatwas not active previously below a question which is not currently theactive question, then a stack and history entry is created, but the nextquestion is determined based on the current question.

After this, the next question to be displayed to the user is determined,step 325. In case of multiple calls, the first uncalled call questionwill be the next question identifier. If all calls were already made,the first call will be the next question identifier. If there are nocalls at all, then the next question displayed is the next one in thequestion history for the current stack. If no entry exists in thequestion history table, the question navigation table may be consultedand the next question determined.

As a result, a new decision tree is automatically generated based on anyquestion selected by a user to be presented and any answer provided.This is made possible by the discrete storage of storing questions,navigation logic, answers, expressions and other data in separate,easily editable tables, and the use of a backend application to processand reprocess this data.

The processes of generating a decision tree, updating the decision tree,and making recommendations all rely on the evaluation of expressions.The data structures used in some embodiments to store expressions weredescribed above. A process for evaluating expressions is illustrated inFIG. 6. Based on an expression identifier retrieved from another of thetables, the expression record is retrieved from the Expression table,step 350. The expression identifier is also used to identify andretrieve one or more records from the expression component table, step355.

For each record in the expression component table retrieved, theexpression components are evaluated by, in some embodiments, retrievingthe identified question option identifier identified for each componentfrom the answer table, step 360, and evaluating the retrieved dataagainst the value stored in the other expression component using acomparator identified in the operator data field, step 365. The resultis a value of true or false for the expression component. If there aremultiple expression components having the expression identifier, step370, the logical values of each evaluated expression component arecombined by a Boolean AND operation, step 375. If an OR Booleanexpression identifier field in a given expression component has a value,step 380, the expression component is combined with the evaluatedexpression component matching the OR expression identifier by a BooleanOR operation, step 385. The resulting logical value is returned towhatever process was requesting it, step 390.

One process which relies on expressions being evaluated is the processof making decisions or recommendations based on the provided answers.Recommendations may be provided at any point during a decision makingsession, based on whatever questions have been answered to that point.Also, in some embodiments, a user may request a recommendation forelements or objects having a certain profile type or profile level,identified in the profile tables, as described above. A process formaking recommendations is illustrated in FIG. 7. When a recommendationis requested, all recommendation records in the recommendations tablehaving expression identifiers affected by stored answers are retrieved,step 400. If the expression is true, step 405, the recommendation recordor records having that expression are marked as triggered, step 410.Those recommendation records are checked to determine whether they arepart of a recommendation category, step 415. If it is, the identifiedrecommendation category record is retrieved, step 420, from therecommendations category table. The recommendation category stores acategory scope bitmask field, as explained above, which is given one ofthree values for the recommendation. The value for this field isretrieved, step 425. Depending on the value, the recommendation ismarked as always shown, step 430, shown for an identified profile type,step 435, or shown for an identified profile level, step 435. Finally, areport is produced showing all recommendations which have been marked,step 440. The report includes the recommendation text, recommendationimportance, and category title and description, as available.

While the invention has been described and illustrated in connectionwith preferred embodiments, many variations and modifications as will beevident to those skilled in this art may be made without departing fromthe spirit and scope of the invention, and the invention is thus not tobe limited to the precise details of methodology or construction setforth above as such variations and modification are intended to beincluded within the scope of the invention.

1. A computerized method for facilitating decision making by presentingquestions to and receiving answers from a user, the method comprising:storing one or more user-editable question tables containing a pluralityof questions and navigation logic data for navigating between questions;maintaining one or more dynamic tables containing question history dataidentifying which of the questions have been presented in a decisionmaking session and answer data identifying answers received from theuser; at a given point in a decision making session, determining whichone or more questions to present based on the question history data andthe navigation logic data; generating a structured document containingthe one or more questions determined to be presented; and generating auser interface using the structured document for presenting the one ormore questions and receiving the answers. 2-24. (canceled)